Magnum One

home *** CD-ROM | disk | FTP | other *** search

/ Magnum One / Magnum One (Mid-American Digital) (Disc Manufacturing).iso / d19 / pcbv31b6.arc / PCBV30.DOC < prev next >

Wrap

Text File | 1989-12-28 | 39.2 KB | 864 lines

PCBVerify 3.0 Callback Verification Door Software Copyright (c) 1987, 1988, 1989 by Curtis Kowalski PROGRAM DESCRIPTION ------------------- PCBVerify is a 'door' type program designed to run in conjunction with various types of bulletin board system (BBS) software which automatically handles verification of new users to the system by establishing callback verification. The user enters the door and enters his phone number. Extensive checks are done to determine if the number is allowed at all, and if so, what time of day it may be dialed, etc. The door then drops carrier on the user and immediately dials the number the user entered. If no modem is found at the opposite end the results are stored and the software recycles to the BBS. If carrier is detected the user is asked to enter his password. If the password is correctly entered the user's security is upgraded along with several other settings as defined by the Sysop. STANDARD "DEMO" LICENSE ----------------------- PCBVerify is a 'Shareware' type program. I encourage everyone to upload and share the code. Several limitations must be implied however: 1) Under no circumstance should the code be modified or distributed in any other form than in that which it was originally supplied (the original is ZIPped, but it may be distributed in other forms so long as the de-compressed form of the program remains the same). 2) PCBVerify may not be redistributed in any other manner than by electronic file transfer except in cases approved by the author. Receiving money for the PCBVerify program itself is absolutely forbidden to anyone but the author, except for telecommunications / service charges. No fee of more than $5.00 shall be collected in such an instance. PCBVerify may be run for an adequate amount of time to allow a full testing of the software. If, after running the code for one month, you do not purchase the registration license (cost is $15.00 US) then this license is terminated and you must remove all working copies of PCBVerify from your system. PCBVerify may be distributed on ANY bulletin board system anywhere. The demo version may not be "hacked" or modified in ANY manner, including but not limited to modifications leading to the enabling of the extended features outlined in this document which are labeled as being available only to those systems running PCBVerify with an authorized PCBVerify Registration Number. Under no circumstance may anyone use a registration number in use by another individual. The Standard "Demo" License as outlined above may be withdrawn by the author of PCBVerify at any time without exception. REGISTRATION LICENSE -------------------- Users that decide to purchase a PCBVerify Registration Number receive several benefits as outlined below. 1) Once purchased, the registration license is non-refundable. However, please note that the registration license is guaranteed for the life of the individual purchasing the license. All future releases of PCBVerify that are written by Curtis Kowalski, its present author, will be compatible with any registration license and PCBVerify Registration Number sold. If this agreement is not satisfied at any time, the author shall be liable for no more than $15 and only in the event that an honest attempt to contact the author and resolve the situation was made and the situation remained unresolved. 2) The registration license authorizes use of all features marked in this documentation as "Registered Version Only." 3) The registration license entitles the holder to free access to Premier BBS, the location of support maintained by the author, so long as the holder of the license adheres to the policies of said BBS. Note that Curtis Kowalski may not be held liable in any manner for not supplying said access unless a request was made and access was knowingly and purposely denied without probable cause. 4) The registration license is non-transferable. The name of the bulletin board registered may be changed if evidence is given that such a change will take place. It is expressly forbidden to use the old registration number once a new one is issued. DISCLAIMER ---------- The author of this software, Curtis Kowalski, is not liable for any lost funds, equipment, or data due to the use of this program except under circumstances where it can be shown that code was intentionally written to do so. BETA TESTING ------------ Each version of PCBVerify is extensively beta tested on my system and several close to me, along with bulletin boards choosing to beta test my software throughout the world. Basically, I try to make sure that when you get a copy of the 'released' version that there is nothing in there that could possibly go wrong. Please realize that, though every effort is made, some things may slip through. If this is the case please notify me immediately - despite all the legal garbage at the beginning of this file I'll be glad to take care of any problem you might have. If you are interested in becoming a beta tester for future releases of PCBVerify, please let me know via Premier BBS. All that is required is that you run the latest PCBVerify version available to you and that you check in with Premier BBS regularly to obtain upgrades and report on how well things are running. PCBVERIFY - CONFIGURATION MADE EASY! ------------------------------------ The long overdue setup program has been completed. After working on PCBVerify several months I was beginning to realize just how difficult the configuration was becoming, especially after making a major mistake of my own in the doc. file of 3.0 beta 6. Although it is a 'quick and dirty' utility it should speed the configuration process of PCBVerify up quite a bit. I will still include the file formats for you in the doc. file as many of you will probably need to modify the configuration file at some time after you do the initial setup. PCBV.CNF (configuration file overview) -------------------------------------- For a complete description of each entry see the following section. Line Description Example ---- ----------- ------- 1 PCBVerify config file identifier PCBVerify ... ("PCBVerify 3.0 Config File" only) 2 Comport to use COM1: (COM1 or COM2) 3 Baud rate lock in? 19200 (the baud rate to lock in at or N) 4 Location and name of "SYS" file D:\PCB\PCBOARD.SYS (location of PCBOARD.SYS or PCBV.SYS) 5 Software type identifier PCB14 (PCB14, PCB12, PCBSYS12, PCBSYS14, or PCBVSYS) 6 Name of your system Premier BBS 7 Registration number 0 (0 = demo copy) 8 Users file or 'results' file D:\PCB\MAIN\USERS (results file used for non PCBoard systems - may be parsed by another program run after PCBVerify). 9 Log file (caller log for PCB12/14) D:\PCB\MAIN\CALLER1 10 Security level of 'new user' 10 11 Security level to increase user to 20 after verifying 12 Difference in time limit of new user 15 and verified user in minutes (number of minutes to add to time limit after verified) 13 New D/L limit of user in Kbytes 9999 (9999 = unlimited for PcBoard) 14 Add number to trashcan if verified? y (Y or N, registered copies only) 15 Add long distance number to trashcan after 1st try regardless of results y 16 Create a special file and give the user a message saying "Running external registration door" if # not allowed? n (if yes, filename supplied instead) 17 Callback mode enabled? y 18 New expiration date for user or +X +365 (+365 = add 365 days to current date to calculate new expiration date) 19 New expired security for user 10 PCBV.CNF (configuration file - line by line description) -------------------------------------------------------- Refer here when running the setup program if you have any question over the various parameters the program will be asking for. Identifier ---------- This line must exist exactly as shown above in order for PCBVerify to use the configuration file. The setup program generates this automatically. Com port -------- Valid values are Com1 and Com2. Tells PCBVerify which communications port to use. Baud rate lock in? ------------------ If you are running a special setup and need to lock your modem in at a specific baud rate at all times, place the baud rate here. If not, simply place an 'n' on this line and PCBVerify will open the modem at the baud rate of the caller. "SYS" file name & location -------------------------- This entry tells PCBVerify the location and name of your "PCBOARD.SYS" file if you are running PCBoard or a [software] to PCBoard converter. If you are using a utility to create the "PCBV.SYS" file (outlined later in this document) this entry tells PCBVerify the location and name of that file. Type of system you are running ------------------------------ This entry defines the type of BBS software you are running. If running a package that creates a PCBoard.Sys of the 12.1 type, place PCBSYS12 on this line - the same is true for version 14, only you instead place PCBSYS14. If actually using PCBoard place PCB14 or PCB12 depending on which version you are running. Finally, if you are running a utility to handle the PCBV.SYS format outlined later in this document place PCBVSYS on this line. Note that this version of PCBVerify does *NOT* support versions of PCBoard prior to 12. Name of your system ------------------- Place the name of your bulletin board as it should appear when running the program on this line. If registered this line *MUST* match the system name you supplied when you registered the code. If you wish to change the name after registering you must contact the author and a new registration number will be supplied. Registration number ------------------- Place a 0 on this line if you are running the demo copy of PCBVerify. If you have registered your code place the registration number you were supplied with on this line to enable the registered software. Users file or 'results' file ---------------------------- If you are using PCBoard BBS software place the full location of your USERS file on this line. If using PCBSYSxx as your system type this line instead defines the location and name of your 'result' file which is created if the user was verified. This file must be a different filename for each node if more than one node is using your PCBVerify working directory. Log file -------- If you are running PCBoard 12 or 14 this line contains the name and location of your callers' log. Otherwise this line should contain the name of an text file that will record each user's name and anything that the user performed while inside of the door. Security level of new user -------------------------- This is the security level of a new user. If a user enters the and his/her security level does not match this number then they will either be redirected to the callback routines or denied entry into PCBVerify. This value is always ignored if running under the PCBSYSxx mode (line 5) and verification mode is assumed. Security level or raise user to after verification -------------------------------------------------- This is the security level you wish to give a user after he/she has been verified successfully. If running under the PCBSYSxx mode (line 5) this parameter will be ignored. Number of minutes to add to time limit after verifying ------------------------------------------------------ This is the number of minutes you wish to add to a users' time limit after he/she has been verified. New D/L limit of user --------------------- This is the new d/l limit in Kbytes to give a user after he/she has been verified. For PcBoard 9999 is unlimited, but for non- PcBoard systems this will depend on the software you are running. Add number to trashcan after verified? -------------------------------------- This option is available only on the registered version and is ignored on the demo copy. If a user is verified and this flag is set to 'y' (and the copy you are running is registered) his/her number will be added to the PCBVTC file and will not be dialed if entered into PCBVerify again. Add number to trashcan if long distance ... ? --------------------------------------------- This option (also available only on the registered version) allows you to add any long distance number to the trashcan after one attempt to avoid persistent callers from trying over and over again to get verified at a long distance number and not succeeding. This should cut down tremendously on the phone bill. Create external registration 'flag file'? ----------------------------------------- If you place an 'n' in this field, if PCBVerify has been given a number that is not allowed for dialing it will return to PCBoard or the software that you are running. You can have it create a file by placing the filename on this line (the filename must be different for each node as with the results file if you are using the same PCBVerify working directory for more than one node). Your batch file may then check for this file's existence and branch to an external registration door (such as a script questionairre type door). Callback mode enabled? ---------------------- One of the newest features in PCBVerify is a callback mode. PCBVerify automatically detects if a user is not in the door for verification and will jump immediately into callback mode if you have place a 'y' on this line. If you instead placed an 'n' then if the user's security is not equal to the 'new user security level' outlined above he/she will be denied access to the door. New expiration date to give user -------------------------------- This entry allows Sysops running under software which includes a 'subscription mode' type setup (such as PCBoard 12/14) to set the users' subscription expiration date to a specific date or a certain number of days in the future. If you are using only the PCBSYSxx mode then this entry will be ignored. Otherwise you may place either a date in the form (yymmdd) or a +X where X = the number of days in the future (from the current system date) to set the expiration date to. For example, if you are running a BBS like Premier which has both subscribing and non-susbcribing members you can prevent having to run PCBSM to reset expiration dates of non-subscribers by having PCBVerify set the expiration date to 0 as it verifies each new user. New expired security to give user --------------------------------- This entry, also for subscription mode type software, defines the expired security level to place in the USERS file (or PCBV.SYS file). PCBV.SYS FILE ------------- The PCBV.SYS file was designed so that those of you running non-PcBoard systems (especially if you designed that system yourself) would be able to run PCBVerify. By writing a two-way conversion utility you can use this file format to interface with any BBS software you might be running that supports DOORs. Note that if a future standard is reached on DOOR.SYS PCBVerify will support it. For the time being, however, I feel it is in order to go ahead and develop a sequential file for passing parameters to and from PCBVerify. Each line of this file is outlined below. To use the PCBV.SYS file format, set your system up using the setup utility and tell it you are using PCBV.SYS, then give it the other parameters necessary. PCBV.SYS file overview ---------------------- Line Description ---- ----------- 1 Computer to modem baud rate 2 Modem to modem baud rate (or Local) 3 Graphics mode on? (Y,N, or 7 for 7-e-1) 4 First name of caller 5 Caller's full name 6 Caller's password 7 Page length of caller 8 Caller's security level 9 Caller's time available on system 10 Caller's download byte limit 11 Caller's EXPIRED security level 12 Caller's expiration date in yymmdd format PCBVERIFY OPERATION ------------------- Invocation of PCBVerify (usually done by the BBS software running a batch file) is pretty straightforward. Below is a sample batch file for invoking PCBVerify. cd \pcbv if exist xreg1 del xreg } delete various 'flag files' pcbv30 pcbv.cnf /network } invokes program using PCBV.CNF as the configuration file and runs PCBVerify in network mode if exist xreg1 xreg.bat } invokes xreg.bat if the user entered a number that was not allowed (and PCBVerify was configured to do so) cd \pcb board } Returns to PcBoard If you are running a non-PcBoard system and wish to write your own software to the security level etc. of the user if he/she was verified, use a batch file similar to the one below. cd \pcbv if exist result1 del result1 } deletes result 'flag file' ... (same as above until the line below) if exist xreg1 xreg.bat if exist result1 upgrade.bat } Checks to see if PCBVerify created result1 (verified flag file) and if so invokes upgrade.bat ... (re-run your BBS software) MULTI-NODE OPERATION -------------------- PCBVerify performs share-compatible reads/writes with all files unless specified as being non-network compatible files. In the event that the files are not network comptabile, your configuration for each node must specify a different filename. Usually the best method of doing so is to append a '1', '2' (etc.) to the end of the filename. The files NOT compatible between nodes are listed below. SYS file (PCBoard.Sys of PCBV.SYS) LOG file (callers' log or textfile for PCBVerify log) RESULT file (for non-PcBoard systems only, created if user is verified) XREG file (created if telephone number not allowed and system has been configured to create this file) All that is required of PCBVerify to enable the network mode is to place the '/NETWORK' switch on the command line AFTER the configuration file. Please note that when running setup it is important to run it for EACH node that you running. Each node must have a different config file regardless. Usually the best way to handle this is to name them as PCBV1.CNF, PCBV2.CNF, etc. FILENAMES --------- The following files (previously configurable, but now hardcoded) must exist in your PCBVerify working directory. WELCOME > initial user instructions (verification mode) CALLBACK > initial user instructions (callback mode) GOODBYE > user goodbye message (given after user is verified) PCBVTEXT > file containing all text messages that appear The above four files must also exist with extensions for each foreign language that may be passed in your PcBoard.Sys file. For example, even if you do not have a French translation of PCBVTEXT, you must copy your 'default' PCBVTEXT to PCBVTEXT.FRE if you are running PCBoard with a French setup. NOTE: If you are capable of translating any of the files listed into a foreign language or if you have, please share them by uploading them to Premier BBS (number listed at the end of this file) PCBVAL > allowed numbers file listing (described in full detail later in this file) PCBVTC > phone trashcan file (described later) PCBVTIME > time formats file (described later) If you have a current setup of PCBVerify that contains any of these files under a different name, please check to see that no changes have been made to that file's format and then simply rename your file to the name listed above. MODEM COMPATIBILITY ------------------- PCBVerify's modem tolerance has been enhanced substantially. Support is now available for error correction type modems such as the HAYES 9600 V-SERIES without having to pass special parameters to the modem to turn off the negotiation process codes. PCBVerify will wait for a line of data to come in that contains a recongizable result code string similar to that of the HAYES standard. The valid result codes are parsed by the software and if they contain any of the following strings are handled as described. "NO ANS" --> call retried "BUSY" ----> call retried "NO DIAL" -> call retried (not counted in the standard 2 attempts) "NO CARR" -> call retried "CONNECT" -> call assumed connected at same baud rate "RING" -> callback aborted - incoming call detected One configuration parameter that you should make sure of - dialtone checking must be ON! If not you may experience some security problems since you will not be able to guarantee that a number was actually called back. If you have problems with modem compatibility please report them to me at Premier BBS, (615) 675-3244. Include a ZIPped copy of your configuration (PCBVAL and PCBV.CNF files) along with a description of the problem and what modem you are running. PCBVTC FILE ----------- The phone number trashcan file (PCBVTC) is used primarily as a place to store any telephone numbers that you do not want PCBVerify to dial (such as the numbers of other local BBS's) and as a database of all numbers that PCBVerify has previously verified and should not be attempted again. Every phone number entered into PCBVerify is placed in this file (if you have configured PCBVerify to do so and are running the registered version). This file is also used to store telephone numbers that you do not want dialed. To do this simply place the complete phone number in the file, in the following format: aaa-ppp-ssss Example: 615-675-3244 | | | | | suffix Note: Wildcard characters are | prefix accepatble, for example, you areacode may enter 615-966-????. Following the phone number entry you may place any comment you wish to add. PCBVerify uses the remaining space on each line it adds to the file to store the name of the user, the time and date the number was trashcanned, and if the number was placed in the file due to it being a long distance number attempted more than once it denotes the entry as such. For example: 615-675-3244 : KOWALSKI, CURTIS : 03-25-1989 (Long distance) | | | | phone number | date of verify | last, first | flags an entry that was not verified on the first try but was long distance Plans to make a 'purge' program to remove these entries as well as a sort routine to create a phone book are currently in effect. NOTE: The demo version of PCBVerify will read from only the first ten lines of the PCBVTC file and will NEVER write to this file no matter how your system is configured. PCBVTIME FILE ------------- The PCBVTIME file is used in conjunction with the PCBVAL file to determine what time of day a number or group of numbers may be dialed. This feature will help cut down phone costs. The PCBVTIME file is a line by line file that consists of five entries, each separated by a comma. Shown below is a diagram of the PCBVTIME file. A, 23:05, 07:55, 23:05, 16:55 (see below for complete descriptions | | | | | of each entry) | | | | Weekend 'stop time' | | | Weekend 'start time' | | Weekday 'stop time' | Weekday 'start time' Time period letter that appears in PCBVAL PCBVTIME PARAMETERS ------------------- Weekday 'start time' = This is the time to start allowing entries with this format letter to be dialed. Weekday applies for Monday through Friday. Weekday 'stop time' = This is the time to stop allowing entries with this format letter to be dialed. Weekend 'start time' = the time (Friday) to start allowing entries with this format letter to be dialed. PCBVerify will start allowing the number Friday at this time and stop on Sunday at the following time. Weekend 'stop time' = the time (Sunday) to stop allowing entries with this format letter to be dialed. Note that the 'weekend' begins Friday at the specified time and ends Sunday at the specified time. Therefore, each format letter defined will be permitted all day Saturday. The Sysop may define up to 26 different time periods, one for each letter of the alphabet. After setting a time period up in the PCBVTIME file, include the letter you configured it for in each entry of PCBVAL you wish to use the PCBVTIME entry defined. NOTE: The demo version of PCBVerify will read only the first line of this file and will use that time range for all entries in the PCBVAL file. PCBVAL FILE ----------- The PCBVAL file is used to tell PCBVerify what phone numbers it may call and how to go about doing so. The Sysop defines what number(s) it can dial (exchange, prefix, suffix, and what the user has answered to the long distance question), when they can be dialed (used in conjunction with the PCBVTIME file), and what to send to the modem when dialing the number that matches that PCBVAL entry. The PCBVAL file consists of one line for each phone number criteria you wish to give it. There are several options, each separated by a comma. Shown below is the general PCBVAL format. 615-???-????,A,N,A,"ATDT" *** *** **** * * * **** | | | | | | | | | | | | | dial string to send | | | | | | | | | | | time period to allow calling | | | | | | | | | long distance flag (compared to users' answer) | | | | | | | format letter (see section below) for dialing | | | | | suffix (? marks used as a wildcard character) | | | prefix | areacode PCBVerify compares the number the user entered with each entry in PCBVAL (starting at the top of the file) until it finds an entry that matches. Therefore, the more specific entries should be placed at the beginning (the ones with the fewest wildcards). PCBVerify will compare the prefix, suffix, and areacode, as well as the long distance question's answer. If the number the user entered matches with the number in PCBVAL and the long distance question flag and question have the same answer, that line will be use for dialing the user's number. If not, PCBVerify will go to the next line and keep going until it reaches a matching entry or the end of the file. If the end of file marker is reached and no match is made, PCBVerify notifies the user that the number is not available for callback. Format letters -------------- The format letter helps PCBVerify decide how to dial the telephone number (e.g. ATDTxxx-xxxx or ATDT1-xxx-xxx-xxxx, etc.) and whether or not to return the user to the board after connecting and updating his/her security level. The table below shows each format letter and how it affects dialing. Key: [ppp] = prefix user entered [ssss] = suffix user entered [aaa] = areacode user entered A -- Dial [ppp]-[ssss] -- Stay connected B -- Dial 1-[ppp]-[ssss] -- Stay connected C -- Dial 1-[aaa]-[ppp]-[ssss] -- Stay connected D -- Dial [ppp]-[ssss] -- Disconnect E -- Dial 1-[ppp]-[ssss] -- Disconnect F -- Dial 1-[aaa]-[ppp]-[ssss] -- Disconnect G -- Dial [aaa]-[ppp]-[ssss] -- Stay connected H -- Dial [aaa]-[ppp]-[ssss] -- Disconnect I -- Dial [ssss] -- Stay connected J -- Dial [ssss] -- Disconnect Sample PCBVAL file ------------------ 615-???-????,A,N,A,"ATDT" 615-???-????,E,Y,B,"ATDT" ???-???-????,F,Y,B,"ATDT" The above file allows local calls (user said not long distance and the number was within the 615 area code) to be dialed. For exmaple, if the user entered 615, 555, 1212, Y as their entries to each prompt in PCBVerify, PCBVerify would send the following string to the modem: ATDT 555-1212 and would stay connected afterwards, returning the user to the board. Long distance calls within the 615 areacode (user said that it was long distance and was a 615 number) would be dialed as: ATDT 1-555-1212 and would be disconnected after the user entered his/her password. Long distance calls outside of the 615 areacode (user said that it was long distance, and put in an areacode other than 615) would be handled by the third line. Say the user put in 201, 555, 1212, for the areacode, prefix, suffix, and long distance question respectively. PCBVerify would send ATDT 1-201-555-1212 to the modem and would disconnect after the user entered his/her password. REGISTERING PCBVERIFY --------------------- In order to register PCBVerify, either fill out the last page of this document and send it to the address shown along with a check for $15.00, or call Premier BBS and follow the instructions up until you get to the main menu, at which point you are can type OPEN 5. If asked for a password, it is SUFFIX. After reaching the door menu, select menu option 1 and then give the system the information requested. You must have a Visa, Mastercard, or Discover to use this method of registering. You will then be given a registration number. After placing this number in your configuration file you will have a full registered version of PCBVerify for this and all future releases. Why register? You are technically required to register PCBVerify after running it for a period of longer than one month. However, I am aware that many people will not adhere to this policy, and have therefore provided a number of other 'advanced' features that registered systems receive, as an incentive. Among these is the capability to add numbers to the PCBVTC file after they have been dialed / verified and also to define various time 'windows' for long distance calls, etc. PREMIER BBS ----------- NOTE: For those of you that were previously registered on Premier and have not heard, the number has changed but the phone company is not notifying callers to the old number. If you were registered at the old number you will be registered at the new one as well, with the same password as before. Premier BBS (615) 675-3244 24 hours per day / everyday Curtis Kowalski, Sysop Sysops that request access to Premier will be granted extended privileges only on request. Since there are many people that call Premier only once or twice to register PCBVerify it is difficult and often useless to try to keep track. I will grant extended access to any Sysop, all you must do is ask nicely... Special thanks to all the boards and Sysops that gave recommendations to me for future versions of PCBVerify. I hope that I've done a good job and that all of you enjoy it! PCBVERIFY REGISTRATION FORM --------------------------- Sysop name: _________________________________________ Address: _________________________________________ City, State, Zip: _________________________________________ Home phone number: _________________ Board(s) to register: (EXACTLY as you want it to appear on screen) ___________________________________ Phone: ___________ ___________________________________ Phone: ___________ ___________________________________ Phone: ___________ Make your check for $15 payable to Curtis Kowalski and mail to: Curtis Kowalski PCBVerify Registration 616 Lark Meadow Drive Knoxville, Tn. 37922 You will receive your registration number a few days after I receive your form. If you do not receive a registration number after approximately 3 weeks, please contact Premier BBS.